- Thank you received: 0
×
Questions about B100/200/400/800 ISDN BRI Cards
[Solved] B200P - alarms RED
14 years 10 months ago #3424
by SnOwMaN
It' seems to me wctdm24xxp is normal module for the TDM410 series, the wctdm was for the old TDM400.
It was the one witch was selected in the dahdi installation with "make config", and it was working fine, so i have unload all the useless modules including wctdm.
It was the one witch was selected in the dahdi installation with "make config", and it was working fine, so i have unload all the useless modules including wctdm.
14 years 10 months ago #3425
by SnOwMaN
I think i have found the problem, i connect my B200P card to un equipement provide by my telecom operator, equipement witch is an NT1/2, so my card should work in TE mode if i'm not wrong. I don't have any DDI all calls arrive at the same number.
but the dmesg seems to say it's not the case, either i have put the wrong jumpers in, or there is another issue.
but dahdi is configure in TE mode, point to multi point
chan_dahid.conf
Can you confirm that B200P should be configure in TE mode when connected to an NT1 equipement ?
i] Last edited by SnOwMaN at 2009-6-24 00:19 [/i
but the dmesg seems to say it's not the case, either i have put the wrong jumpers in, or there is another issue.
[ 21.441723] wcb4xxp 0000:01:08.0: probe called for b4xx...
[ 21.441758] wcb4xxp 0000:01:08.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 21.442111] wcb4xxp 0000:01:08.0: Identified OpenVox B200P (controller rev 1) at 0001e8f8, IRQ 17
[ 21.443558] wcb4xxp 0000:01:08.0: NOTE: hardware echo cancellation has been disabled
[ 21.443661] wcb4xxp 0000:01:08.0: Port 1: NT mode
[ 21.443778] wcb4xxp 0000:01:08.0: Port 2: NT mode
[ 21.444256] wcb4xxp 0000:01:08.0: Did not do the highestorder stuff
[ 21.541861] dahdi_echocan_mg2: Registered echo canceler 'MG2'
[ 21.546049] dahdi: Registered tone zone 2 (France)
[ 21.613262] wcb4xxp 0000:01:08.0: new card sync source: port 2
[ 23.513281] wcb4xxp 0000:01:08.0: new card sync source: port 3
[ 26.680043] eth0: no IPv6 routers present
[ 5416.005176] dahdi_echocan_mg2: Registered echo canceler 'MG2'but dahdi is configure in TE mode, point to multi point
chan_dahid.conf
[channels]
usecallerid=yes
hidecallerid=no
immediate=yes
echocancel=yes
context=default
hanguponpolarityswitch=yes
; Span 1: WCTDM/0 "Wildcard TDM410P Board 1" (MASTER)
;;; line="3 WCTDM/0/2 FXSKS (In use) (EC: MG2)" -- RTC
signalling=fxs_ks
callerid=asreceived
group=0
context=external_RTC
;context=from-pstn
channel => 3
context=default
;;; line="4 WCTDM/0/3 FXSKS (In use) (EC: MG2)" -- Livebox
signalling=fxs_ks
callerid=asreceived
group=0
;context=from-pstn
context=external
channel => 4
context=default
; Span 2: B4/0/1 "B4XXP (PCI) Card 0 Span 1"
group=0,12
context=from-pstn
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel => 5-6
context = default
group = 63
; Span 3: B4/0/2 "B4XXP (PCI) Card 0 Span 2"
group=0,13
context=from-pstn
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel => 8-9
context = default
group = 63Can you confirm that B200P should be configure in TE mode when connected to an NT1 equipement ?
i] Last edited by SnOwMaN at 2009-6-24 00:19 [/i
14 years 10 months ago #3432
by james.zhu
hello:
are you using Digium analog card with our BRI card? your side must be TE mode. where do you get the full package for dahdi-bri? make sure this is a completed package.
==========sample======================
loadzone=nl
defaultzone=nl
# qozap span definitions
# most of the values should be bogus because we are not really zaptel
span=1,1,0,ccs,ami
span=2,2,0,ccs,ami
span=3,3,0,ccs,ami
span=4,4,0,ccs,ami
bchan=1,2
hardhdlc=3
bchan=4,5
hardhdlc=6
bchan=7,8
hardhdlc=9
bchan=10,11
hardhdlc=12
============chan_dahdi.conf=============
[channels]
;
; Default language
;
;language=en
;
; Default context
;
;
switchtype = euroisdn
echocancel=no
; p2mp TE mode (for connecting ISDN lines in point-to-multipoint mode)
signalling = bri_cpe_ptmp
; p2p TE mode (for connecting ISDN lines in point-to-point mode)
;signalling = bri_cpe
; p2mp NT mode (for connecting ISDN phones in point-to-multipoint mode)
;signalling = bri_net_ptmp
; p2p NT mode (for connecting an ISDN pbx in point-to-point mode)
;signalling = bri_net
pridialplan = local
prilocaldialplan = dynamic
nationalprefix = 0
internationalprefix = 00
priindication = passthrough
echocancel = yes
context=demo
group = 1
; S/T port 1
channel => 1-2
group = 2
; S/T port 2
channel => 4-5
group = 3
; S/T port 3
channel => 7-8
group = 4
; S/T port 4
channel => 10-11
regards!
James.zhu
are you using Digium analog card with our BRI card? your side must be TE mode. where do you get the full package for dahdi-bri? make sure this is a completed package.
==========sample======================
loadzone=nl
defaultzone=nl
# qozap span definitions
# most of the values should be bogus because we are not really zaptel
span=1,1,0,ccs,ami
span=2,2,0,ccs,ami
span=3,3,0,ccs,ami
span=4,4,0,ccs,ami
bchan=1,2
hardhdlc=3
bchan=4,5
hardhdlc=6
bchan=7,8
hardhdlc=9
bchan=10,11
hardhdlc=12
============chan_dahdi.conf=============
[channels]
;
; Default language
;
;language=en
;
; Default context
;
;
switchtype = euroisdn
echocancel=no
; p2mp TE mode (for connecting ISDN lines in point-to-multipoint mode)
signalling = bri_cpe_ptmp
; p2p TE mode (for connecting ISDN lines in point-to-point mode)
;signalling = bri_cpe
; p2mp NT mode (for connecting ISDN phones in point-to-multipoint mode)
;signalling = bri_net_ptmp
; p2p NT mode (for connecting an ISDN pbx in point-to-point mode)
;signalling = bri_net
pridialplan = local
prilocaldialplan = dynamic
nationalprefix = 0
internationalprefix = 00
priindication = passthrough
echocancel = yes
context=demo
group = 1
; S/T port 1
channel => 1-2
group = 2
; S/T port 2
channel => 4-5
group = 3
; S/T port 3
channel => 7-8
group = 4
; S/T port 4
channel => 10-11
regards!
James.zhu
14 years 10 months ago #3433
by SnOwMaN
Yes i'm using both analog Digium and Openvox BRI in the same machine.
For the dahdi-bri, i have used the last version of dahdi witch include an extended support of bri cards, and then i patch it for the Openvox B200P support with the patch you had tested here . I also installed the libpri package.
And my card is detected as Openvox B200P
dahdi_hardwareAs i'm using both analog and bri, my dahdi/system.conf is sighlty different:It was auto-generatd by dahdi_genconf, and modify for fr zone, and echocanceller.
In your sample you seems to use hardhdlc for the signalisation channel, so i should use hardware signalisation rather than dahdi signalisation ?
For the dahdi-bri, i have used the last version of dahdi witch include an extended support of bri cards, and then i patch it for the Openvox B200P support with the patch you had tested here . I also installed the libpri package.
And my card is detected as Openvox B200P
dahdi_hardware
pci:0000:01:07.0 wctdm24xxp+ d161:8005 Wildcard TDM410P
pci:0000:01:08.0 wcb4xxp+ 1397:08b4 OpenVox B200P# Autogenerated by /usr/sbin/dahdi_genconf on Fri Jun 12 11:10:08 2009 -- do not hand edit
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: WCTDM/0 "Wildcard TDM410P Board 1" (MASTER)
# channel 1, WCTDM/0/0, no module.
# channel 2, WCTDM/0/1, no module.
fxsks=3
echocanceller=mg2,3
fxsks=4
echocanceller=mg2,4
# Span 2: B4/0/1 "B4XXP (PCI) Card 0 Span 1"
span=2,1,0,ccs,ami
# termtype: te
bchan=5-6
dchan=7
echocanceller=mg2,5-6
# Span 3: B4/0/2 "B4XXP (PCI) Card 0 Span 2"
span=3,2,0,ccs,ami
# termtype: te
bchan=8-9
dchan=10
echocanceller=mg2,8-9
# Global data
loadzone = fr
defaultzone = frIn your sample you seems to use hardhdlc for the signalisation channel, so i should use hardware signalisation rather than dahdi signalisation ?
14 years 10 months ago #3434
by james.zhu
hello:
you can try to change to hardhdlc. please make sure your code is fully completed. because there are many patches files, i am really not sure the code. therefore, i am still testing the wcb4xxp. have you noticed that digium still open the issue? please make sure the code is released officially.
you may check with this url:
www.asterisk-es-rsp.org/blog/?p=5
regards!
james.zhu
you can try to change to hardhdlc. please make sure your code is fully completed. because there are many patches files, i am really not sure the code. therefore, i am still testing the wcb4xxp. have you noticed that digium still open the issue? please make sure the code is released officially.
you may check with this url:
www.asterisk-es-rsp.org/blog/?p=5
regards!
james.zhu
Time to create page: 0.047 seconds